Pull Request

According to MeiliSearch docs

The document id must be an integer or a string

However, currently meilisearch-rails always stringifies primary keys before sending them to MeiliSearch. As a result, sorting by primary key becomes impossible, because hits will be sorted alphabetically:

Color.create!(id: 1, name: 'purple', short_name: 'p')
Color.create!(id: 2, name: 'blue', short_name: 'b')
Color.create!(id: 10, name: 'yellow', short_name: 'l')
raw_search_results = Color.raw_search('*', sort: ['id:asc'])['hits']
raw_search_result_ids = raw_search_results.map { |h| h['id'].to_i }

raw_search_result_ids == [1, 2, 10] #> false
raw_search_result_ids #> [1, 10, 2]

What does this PR do?

• adds a stringify_primary_keys configuration which will preserve current behaviour
• if stringify_primary_keys is set to false, meilisearch-rails will not stringify primary keys when sending them to MeiliSearch, and will look up record by integers instead of strings

Ideally full test suite will have to be ran twice, with this config set to true and false; I did so manually when submitting this PR. But I wasn't sure if this PR will be considered so didn't expand specs, other than adding a test which confirms that primary-key-sorted docs will preserve order.

PR checklist

Please check if your PR fulfills the following requirements:

• [+] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
• [+] Have you read the contributing guidelines?
• [+] Have you made sure that the title is accurate and descriptive of the changes?